Presentation: Tweet"Work Smart, Not Hard: Tradeoffs & Techniques for Post Agile Teams"

What does a team do after mastering agile? This talk is centered on the technical tradeoffs and choices teams face in order to progress from what is currently considered 'agile'. The agile manifesto has helped many realize that there is a better way to work. However, this software development lifecycle was founded fifteen years ago. How does that influence decisions and determine outcomes today?

Today, teams are faced with a growing number of decisions and tradeoffs. When do you go to the cloud (and which cloud)? What levels of tests do you need? How do you continuously deliver software (and which tools)? Should we build a native, a responsive or some sort of hybrid-like application? The complexity and breadth of software decisions have skyrocketed.

This talk will focus on the aspect of how technical people need to change, though it will address development processes in general. First we'll start with what to stop doing. Too many authors discuss what best practices are, but not enough cover what you'll encounter as you pursue best practices. How do you know if you're on the right track or if you are veering the wrong direction? Next we'll consider how to and what to prioritize focusing primarily on technical choices. With the complexity of software development growing, you must ensure you are aware of the potential consequences when you make or postpone decisions. Finally we'll talk about what lines need to be blurred. How do the many new technologies, techniques and frameworks that have been introduced since the manifesto fit into your organization? For example, how does "DevOps" fit? Overall, the goal is to help technical people understand how to move from today's agile into something that works with the reality and complexity of today's software development.

Prerequisite attendee experience level: advanced